Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1492

reference
597-tree-1
name
1492
tree-preservation-order

undefined

597-tpo-1
uprn
address-text
point
POINT (-1.021760 50.882079)
geometry
MULTIPOLYGON (((-1.021647 50.882067,-1.021652 50.882089,-1.021668 50.882109,-1.021692 50.882126,-1.021724 50.882136,-1.021759 50.882140,-1.021794 50.882137,-1.021826 50.882127,-1.021852 50.882111,-1.021868 50.882091,-1.021874 50.882069,-1.021869 50.882047,-1.021853 50.882026,-1.021829 50.882010,-1.021797 50.882000,-1.021762 50.881996,-1.021727 50.881999,-1.021695 50.882009,-1.021669 50.882025,-1.021653 50.882045,-1.021647 50.882067)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL